chore: switch to npm staged publishing#61
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 99c564a10f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| uses: ncipollo/release-action@339a81892b84b4eeb0f6e744e4574d79d0d9b8dd # v1 | ||
| with: | ||
| generateReleaseNotes: 'true' | ||
| run: pnpm stage publish --no-git-checks |
There was a problem hiding this comment.
For tag or manual releases, this step invokes pnpm stage publish, but staged publishing is an npm CLI subcommand (npm stage publish); pnpm's documented publish command is pnpm publish ... and this package also has no stage script for pnpm to fall back to. As written, the release job will fail before any package is staged, so the workflow no longer publishes/stages releases.
Useful? React with 👍 / 👎.
This PR switches the release workflow to npm staged publishing with
pnpm stage publishand aligns the repository package manager metadata onpnpm@11.3.0.Related Links: